rework nav for ruby #15591
Merged
rework nav for ruby #15591
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Bundle ReportChanges will increase total bundle size by 4.08kB (0.02%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
| description: "Structured logs allow you to send, view and query logs sent from your Rails applications within Sentry." | ||
| sidebar_order: 5600 | ||
| sidebar_order: 4 | ||
| sidebar_section: features |
There was a problem hiding this comment.
Bug: Duplicate sidebar_order in features navigation section
Both docs/platforms/ruby/logs/index.mdx and this file have sidebar_order: 4 with sidebar_section: features. Duplicate sidebar_order values in the same section will cause navigation ordering conflicts. The Rails-specific guide should have a distinct sidebar_order value to maintain proper navigation hierarchy.
codyde
approved these changes
Nov 27, 2025
philprime
pushed a commit
that referenced
this pull request
Nov 28, 2025
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR See changes on https://sentry-docs-git-feat-ruby-docs-nav-standardized.sentry.dev/platforms/ruby/ and all ruby platforms Sidebar Sections Added 'Features' section with organized feature pages Added 'Configuration' section Both sections now have proper headers and grouping Features Section (sidebar_section: features) Order: Capturing Errors → Logs → Tracing → Profiling → Crons Renamed 'Usage' to 'Capturing Errors' (matching JS) Added 'new' tag to Logs Added 'beta' tag to Metrics Reordered all features for consistency Configuration Section (sidebar_section: configuration) Order: Enriching Events → Extended Configuration → Integrations → Data Management → Security Policy Reporting → Migration Guide → Troubleshooting Follows the pattern established in #15440 <img width="321" height="744" alt="Screenshot 2025-11-21 at 2 48 07 PM" src="https://github.com/user-attachments/assets/238cc32d-0a70-4121-bb96-1aebb167dd53" /> ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Alex Krawiec <alex.krawiec@R7J1Y747QQ.local>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
See changes on https://sentry-docs-git-feat-ruby-docs-nav-standardized.sentry.dev/platforms/ruby/ and all ruby platforms
Sidebar Sections
Added 'Features' section with organized feature pages
Added 'Configuration' section
Both sections now have proper headers and grouping
Features Section (sidebar_section: features)
Order: Capturing Errors → Logs → Tracing → Profiling → Crons
Renamed 'Usage' to 'Capturing Errors' (matching JS)
Added 'new' tag to Logs
Added 'beta' tag to Metrics
Reordered all features for consistency
Configuration Section (sidebar_section: configuration) Order: Enriching Events → Extended Configuration → Integrations → Data Management → Security Policy Reporting → Migration Guide → Troubleshooting
Follows the pattern established in #15440
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES